Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a49e1c0a9278d6a8c52d991e507740cc0d9b41d9aa1f6babc816f22366cbd95

Tx prefix hash: b09bf5d05a56f93b61efc528569fe97c266b5f49a6c02e5e9b2ca5bb5c68fc0b
Tx public key: 3a83808a5ec3011d42d8260d4a98de50c87782d2254725a83eefe1c9b52931e4
Timestamp: 1729180020 Timestamp [UCT]: 2024-10-17 15:47:00 Age [y:d:h:m:s]: 00:222:02:48:37
Block: 1133662 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158563 RingCT/type: yes/0
Extra: 013a83808a5ec3011d42d8260d4a98de50c87782d2254725a83eefe1c9b52931e4021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0596aa8d148a0df53d63f1885593f71e08f521a7b3d1a838e26237bcdc016a5b 0.600000000000 1616843 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": 1133672, "vin": [ { "gen": { "height": 1133662 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0596aa8d148a0df53d63f1885593f71e08f521a7b3d1a838e26237bcdc016a5b" } } ], "extra": [ 1, 58, 131, 128, 138, 94, 195, 1, 29, 66, 216, 38, 13, 74, 152, 222, 80, 200, 119, 130, 210, 37, 71, 37, 168, 62, 239, 225, 201, 181, 41, 49, 228, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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