Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c938546564b108aaeb8f6c20a952b3ca359aae0ad53b954d7164d93fd21319a1

Tx prefix hash: 274c4dca428800de8da4a58542d325d0a3b49396dfe0d21ff8d2500c41e33b15
Tx public key: 83b98f43505b41594f8e7a484a9f20dde66fb5138535cd79555ad704b3b43dae
Timestamp: 1745622409 Timestamp [UCT]: 2025-04-25 23:06:49 Age [y:d:h:m:s]: 00:209:09:41:12
Block: 1269442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147386 RingCT/type: yes/0
Extra: 0183b98f43505b41594f8e7a484a9f20dde66fb5138535cd79555ad704b3b43dae021100000013dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 587c1a7db091f664f0002234856e47d3f92f0f2dae90f0d2eee2c22ad6458df0 0.600000000000 1756681 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": 1269452, "vin": [ { "gen": { "height": 1269442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "587c1a7db091f664f0002234856e47d3f92f0f2dae90f0d2eee2c22ad6458df0" } } ], "extra": [ 1, 131, 185, 143, 67, 80, 91, 65, 89, 79, 142, 122, 72, 74, 159, 32, 221, 230, 111, 181, 19, 133, 53, 205, 121, 85, 90, 215, 4, 179, 180, 61, 174, 2, 17, 0, 0, 0, 19, 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