Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 954c7cebd7545a8c0fb332ecebd1c732153b66331e71a9c46b9da97f8b56198e

Tx prefix hash: ee24510ed381a2eb636c40beccac1bb560001ef2b2c0e8b0c5d0d69237efb235
Tx public key: 38ac0a12be5ccdbf4b9c235ded2fb8ccbf401742d58ff1432a94e56c351f3a46
Timestamp: 1751894211 Timestamp [UCT]: 2025-07-07 13:16:51 Age [y:d:h:m:s]: 00:181:04:07:53
Block: 1320625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128002 RingCT/type: yes/0
Extra: 0138ac0a12be5ccdbf4b9c235ded2fb8ccbf401742d58ff1432a94e56c351f3a46021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c64dcd1ee522a290701dc1b6efaacdb8355b07f6fc015b64ead2a499854b1d5a 0.600000000000 1808324 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": 1320635, "vin": [ { "gen": { "height": 1320625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c64dcd1ee522a290701dc1b6efaacdb8355b07f6fc015b64ead2a499854b1d5a" } } ], "extra": [ 1, 56, 172, 10, 18, 190, 92, 205, 191, 75, 156, 35, 93, 237, 47, 184, 204, 191, 64, 23, 66, 213, 143, 241, 67, 42, 148, 229, 108, 53, 31, 58, 70, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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