Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5ff1c308e8fa1d4925f571e8f3b24012280d9d65a70e69696f65f19c23ff05b9

Tx prefix hash: 4e00cda90aefd468fc3bde22e43993090427fdd444d83a462043126e4e8d08d0
Tx public key: 5bca7a3656010d3e5f2472a61bb3c6aab65cd6171df11f0a40f5f6d440da59ef
Timestamp: 1744473894 Timestamp [UCT]: 2025-04-12 16:04:54 Age [y:d:h:m:s]: 00:030:13:41:48
Block: 1259955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 21862 RingCT/type: yes/0
Extra: 015bca7a3656010d3e5f2472a61bb3c6aab65cd6171df11f0a40f5f6d440da59ef021100000002dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a035b78fb44f4b4c49ece37f81a341122cd36aca23792e92e7007c86c6055c5 0.600000000000 1747106 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": 1259965, "vin": [ { "gen": { "height": 1259955 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a035b78fb44f4b4c49ece37f81a341122cd36aca23792e92e7007c86c6055c5" } } ], "extra": [ 1, 91, 202, 122, 54, 86, 1, 13, 62, 95, 36, 114, 166, 27, 179, 198, 170, 182, 92, 214, 23, 29, 241, 31, 10, 64, 245, 246, 212, 64, 218, 89, 239, 2, 17, 0, 0, 0, 2, 219, 181, 113, 193, 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