Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5126e363e7c00166b645e7cc4b90182a4c418c310e5dd3a80b4bddd8f80c75

Tx prefix hash: 92fb54fc8369e1f3e9c539b79c9f33e15098fc2f9ba285ef13e50bbf658271ca
Tx public key: e7f01aa7b6bada3a35d1a9836f157dc1bcfb0ec5b7cf3d360d418c24d5e78da2
Timestamp: 1687112510 Timestamp [UCT]: 2023-06-18 18:21:50 Age [y:d:h:m:s]: 01:253:19:58:41
Block: 785151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 442555 RingCT/type: yes/0
Extra: 01e7f01aa7b6bada3a35d1a9836f157dc1bcfb0ec5b7cf3d360d418c24d5e78da2021100000007e6d27f9c000000000000000000

1 output(s) for total of 1.536314978000 dcy

stealth address amount amount idx
00: cfdb0ab3c0e7c97e55ba7949e9a07d1908d553e363fd08eb0fed64354e6be6fc 1.536314978000 1235084 of 0

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": 785161, "vin": [ { "gen": { "height": 785151 } } ], "vout": [ { "amount": 1536314978, "target": { "key": "cfdb0ab3c0e7c97e55ba7949e9a07d1908d553e363fd08eb0fed64354e6be6fc" } } ], "extra": [ 1, 231, 240, 26, 167, 182, 186, 218, 58, 53, 209, 169, 131, 111, 21, 125, 193, 188, 251, 14, 197, 183, 207, 61, 54, 13, 65, 140, 36, 213, 231, 141, 162, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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