Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc1cbaecb5fcb98bb515bd89902864cf59a316c1770f6cfbd113afabac2df30e

Tx prefix hash: df0bba27f378d39ceb6c638f8e0de613dd9a48c537b0c4c1949cd1f643001f1b
Tx public key: 6c1fb775c963204f8ed626e608c4a5692d67d86843326fcd680d57e47d2b4ab6
Timestamp: 1721994035 Timestamp [UCT]: 2024-07-26 11:40:35 Age [y:d:h:m:s]: 00:258:11:18:47
Block: 1074080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184644 RingCT/type: yes/0
Extra: 016c1fb775c963204f8ed626e608c4a5692d67d86843326fcd680d57e47d2b4ab6021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c77c9b5c1fc37c300a8f553f2507d6300316fc2be78be4f38eae89bb6930295 0.600000000000 1546593 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": 1074090, "vin": [ { "gen": { "height": 1074080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c77c9b5c1fc37c300a8f553f2507d6300316fc2be78be4f38eae89bb6930295" } } ], "extra": [ 1, 108, 31, 183, 117, 201, 99, 32, 79, 142, 214, 38, 230, 8, 196, 165, 105, 45, 103, 216, 104, 67, 50, 111, 205, 104, 13, 87, 228, 125, 43, 74, 182, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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