Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0c5209aed1f7c204c635a8fc15bd65f72a37441e4f3b66c94a6ccbb06d583d

Tx prefix hash: f902e6ce4e72e5ec387675f5b3ebcd917355eac7d56084fcaa85d9a636485248
Tx public key: 8dd299351abcf917b8416de155d8f7a8a853681e1ed0c876bb65632bf92931e3
Timestamp: 1764953330 Timestamp [UCT]: 2025-12-05 16:48:50 Age [y:d:h:m:s]: 00:031:04:48:16
Block: 1427098 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22367 RingCT/type: yes/0
Extra: 018dd299351abcf917b8416de155d8f7a8a853681e1ed0c876bb65632bf92931e302110000000170609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d313c79fe7f19c5a77a9e6e503b1aac6a2be05b2b6f204560e9651ad02d6acbb 0.600000000000 1915797 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": 1427108, "vin": [ { "gen": { "height": 1427098 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d313c79fe7f19c5a77a9e6e503b1aac6a2be05b2b6f204560e9651ad02d6acbb" } } ], "extra": [ 1, 141, 210, 153, 53, 26, 188, 249, 23, 184, 65, 109, 225, 85, 216, 247, 168, 168, 83, 104, 30, 30, 208, 200, 118, 187, 101, 99, 43, 249, 41, 49, 227, 2, 17, 0, 0, 0, 1, 112, 96, 157, 3, 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