Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: b439e9ac1c5dcca26237fd2fbc659223f0106be65cdb1d7cc18f334ff821c272

Tx prefix hash: fafb61bc440c2252f49e2f586d337a140d7b7a79a253971635796dc5262b7949
Tx public key: b584a52b3020618266c5585d301f08746e1dd9c028206f8f4a6fd13a7b653968
Timestamp: 1760238273 Timestamp [UCT]: 2025-10-12 03:04:33 Age [y:d:h:m:s]: 00:039:04:56:56
Block: 1388028 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28079 RingCT/type: yes/0
Extra: 01b584a52b3020618266c5585d301f08746e1dd9c028206f8f4a6fd13a7b653968021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b093c77086b13338e246e06b44012b24d8471273d0e679f9aca0341050e8930d 0.600000000000 1876223 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1388038, "vin": [ { "gen": { "height": 1388028 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b093c77086b13338e246e06b44012b24d8471273d0e679f9aca0341050e8930d" } } ], "extra": [ 1, 181, 132, 165, 43, 48, 32, 97, 130, 102, 197, 88, 93, 48, 31, 8, 116, 110, 29, 217, 192, 40, 32, 111, 143, 74, 111, 209, 58, 123, 101, 57, 104, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8