Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93f702f37c8d1f7658b5ad8c1c721269dada3e23ca16f4fb7080b534d54c5fe2

Tx prefix hash: 1a91b066565ae7f2ed7b4d34b188a065b38da8ac4d15694d34e552eff10aebfe
Tx public key: 484c35ae6d1b96dac9e6a86b8437ca361099b2e8b11cb1aa473a91f91c234484
Timestamp: 1719725084 Timestamp [UCT]: 2024-06-30 05:24:44 Age [y:d:h:m:s]: 01:176:17:19:49
Block: 1055269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384893 RingCT/type: yes/0
Extra: 01484c35ae6d1b96dac9e6a86b8437ca361099b2e8b11cb1aa473a91f91c23448402110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b79e105674e6d9aa107136c76c99cd2c5adb2eab8a5aa2adac9a78209b75a7f6 0.600000000000 1525666 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": 1055279, "vin": [ { "gen": { "height": 1055269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b79e105674e6d9aa107136c76c99cd2c5adb2eab8a5aa2adac9a78209b75a7f6" } } ], "extra": [ 1, 72, 76, 53, 174, 109, 27, 150, 218, 201, 230, 168, 107, 132, 55, 202, 54, 16, 153, 178, 232, 177, 28, 177, 170, 71, 58, 145, 249, 28, 35, 68, 132, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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