Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc729b6260c36c1acf28478f51eeff4b98732611d90467f6d1552f616ccb9666

Tx prefix hash: 37e28aa0f3bb40a9dfbda9f3ed0b27dd6b383206b0d7a694f7563a5296b94f04
Tx public key: d1d248f45209ec475383c193f0d792669446f4dda069a3482af3326e6dfa8743
Timestamp: 1582517895 Timestamp [UCT]: 2020-02-24 04:18:15 Age [y:d:h:m:s]: 04:309:20:37:57
Block: 71444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1113930 RingCT/type: yes/0
Extra: 01d1d248f45209ec475383c193f0d792669446f4dda069a3482af3326e6dfa8743021100000001c71d3ff9000000000000000000

1 output(s) for total of 355.858359021000 dcy

stealth address amount amount idx
00: af09ccdac2ed7a17ef08cabc67254f574921ecba3d9694c3c6f4cdc83833ddc6 355.858359021000 131945 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": 71454, "vin": [ { "gen": { "height": 71444 } } ], "vout": [ { "amount": 355858359021, "target": { "key": "af09ccdac2ed7a17ef08cabc67254f574921ecba3d9694c3c6f4cdc83833ddc6" } } ], "extra": [ 1, 209, 210, 72, 244, 82, 9, 236, 71, 83, 131, 193, 147, 240, 215, 146, 102, 148, 70, 244, 221, 160, 105, 163, 72, 42, 243, 50, 110, 109, 250, 135, 67, 2, 17, 0, 0, 0, 1, 199, 29, 63, 249, 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