Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f020a9765ea99e8d013d738d067ca982e09c5e71c6134fb4505e99bcd9816d87

Tx prefix hash: 6226c633aeed68607ab12d6007df5b9904699d5e734f6e85e2add38e3b2fe802
Tx public key: fb0d98d13b2e798d1fe843e94b338f89b133fa91517f52d1bd5cc9f9f8188bc7
Timestamp: 1752191471 Timestamp [UCT]: 2025-07-10 23:51:11 Age [y:d:h:m:s]: 00:182:04:04:28
Block: 1322934 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 128859 RingCT/type: yes/0
Extra: 01fb0d98d13b2e798d1fe843e94b338f89b133fa91517f52d1bd5cc9f9f8188bc70211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d2b27c3407257710cae117b541f3357561f0e6addb516fcd89fcf28d4675ef5 0.600000000000 1810667 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": 1322944, "vin": [ { "gen": { "height": 1322934 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d2b27c3407257710cae117b541f3357561f0e6addb516fcd89fcf28d4675ef5" } } ], "extra": [ 1, 251, 13, 152, 209, 59, 46, 121, 141, 31, 232, 67, 233, 75, 51, 143, 137, 177, 51, 250, 145, 81, 127, 82, 209, 189, 92, 201, 249, 248, 24, 139, 199, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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