Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b454c5033952d0da2b3805c237265d1de6bbca756e5507e9309a8d318515a3f

Tx prefix hash: 330982559b7efeefee056fe984bb7e693bafcdd4116d8b0339912a47500aa94b
Tx public key: a6c062ec0d996b76203a618ddd9db6345a16a446b159d06da9c962f8e7d1b276
Timestamp: 1726314169 Timestamp [UCT]: 2024-09-14 11:42:49 Age [y:d:h:m:s]: 00:161:17:05:34
Block: 1109904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115359 RingCT/type: yes/0
Extra: 01a6c062ec0d996b76203a618ddd9db6345a16a446b159d06da9c962f8e7d1b276021100000008e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0dc58f0aa71a93be6b61167380e755d9af40ae70acdad744a978a09363e6ce09 0.600000000000 1588319 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": 1109914, "vin": [ { "gen": { "height": 1109904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0dc58f0aa71a93be6b61167380e755d9af40ae70acdad744a978a09363e6ce09" } } ], "extra": [ 1, 166, 192, 98, 236, 13, 153, 107, 118, 32, 58, 97, 141, 221, 157, 182, 52, 90, 22, 164, 70, 177, 89, 208, 109, 169, 201, 98, 248, 231, 209, 178, 118, 2, 17, 0, 0, 0, 8, 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