Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dde9ed2ded0ffe1387829f3d1b4c819738c2957f4bff6693bac1344d1879d801

Tx prefix hash: 0b0f205c8c561ac5f4bb54818cd0430b2060b135a48b1f3c2ec2907aa68b32a9
Tx public key: 84311d2f4028e13ff1a1d472f4ecde7db2a8a091c5e4dfff397b1b33a59d37da
Timestamp: 1764829844 Timestamp [UCT]: 2025-12-04 06:30:44 Age [y:d:h:m:s]: 00:003:22:13:10
Block: 1426085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2811 RingCT/type: yes/0
Extra: 0184311d2f4028e13ff1a1d472f4ecde7db2a8a091c5e4dfff397b1b33a59d37da021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0ec17261ef5307420b94ed222e19596cfc1937d93954a4ecada9823ddecdc13 0.600000000000 1914768 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": 1426095, "vin": [ { "gen": { "height": 1426085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0ec17261ef5307420b94ed222e19596cfc1937d93954a4ecada9823ddecdc13" } } ], "extra": [ 1, 132, 49, 29, 47, 64, 40, 225, 63, 241, 161, 212, 114, 244, 236, 222, 125, 178, 168, 160, 145, 197, 228, 223, 255, 57, 123, 27, 51, 165, 157, 55, 218, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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