Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f07cc1a1ea8d05a07b0cb271c225e0805a50f591869c16cc5856f5c14719261

Tx prefix hash: ca7f4e1166b19e22153c9276ee53d5ad6d8cbd43aa09fa7e7ebc42102e11449f
Tx public key: f76ed79c60ab8767beef4c942e8f450ea50c14255af1b270025c3cd69548cee4
Timestamp: 1703573480 Timestamp [UCT]: 2023-12-26 06:51:20 Age [y:d:h:m:s]: 01:171:13:17:45
Block: 921374 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383682 RingCT/type: yes/0
Extra: 01f76ed79c60ab8767beef4c942e8f450ea50c14255af1b270025c3cd69548cee402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00c18bc1a02a69b54f29ba1a92923ff923302a35c9f5c23a35a80c3966db4e5b 0.600000000000 1379060 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": 921384, "vin": [ { "gen": { "height": 921374 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00c18bc1a02a69b54f29ba1a92923ff923302a35c9f5c23a35a80c3966db4e5b" } } ], "extra": [ 1, 247, 110, 215, 156, 96, 171, 135, 103, 190, 239, 76, 148, 46, 143, 69, 14, 165, 12, 20, 37, 90, 241, 178, 112, 2, 92, 60, 214, 149, 72, 206, 228, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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