Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f86faada3e906b09c42cdc0b2e55c6581dff3948aa1c3a6580285691ddb46f85

Tx prefix hash: bceb0bf0a85e561335ff2c7c1a944089b1811872948c7ac6201c16d3b2375437
Tx public key: 6cd1075dc06a516c235b4689859ece3f8438edaa52c8eeaf79f129d3f8c61de5
Timestamp: 1708030626 Timestamp [UCT]: 2024-02-15 20:57:06 Age [y:d:h:m:s]: 01:054:19:16:05
Block: 958316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300211 RingCT/type: yes/0
Extra: 016cd1075dc06a516c235b4689859ece3f8438edaa52c8eeaf79f129d3f8c61de502110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e08214f247c8cb4a28d6700c341019d1199ff9c6517cbd66df9818aa8719d64 0.600000000000 1417675 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": 958326, "vin": [ { "gen": { "height": 958316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e08214f247c8cb4a28d6700c341019d1199ff9c6517cbd66df9818aa8719d64" } } ], "extra": [ 1, 108, 209, 7, 93, 192, 106, 81, 108, 35, 91, 70, 137, 133, 158, 206, 63, 132, 56, 237, 170, 82, 200, 238, 175, 121, 241, 41, 211, 248, 198, 29, 229, 2, 17, 0, 0, 0, 19, 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