Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49fff1946c3a96b6c0e13318388c6519d4276265fb1d7508dfbe2227b5e65cdc

Tx prefix hash: 8ffd24617ff33a4942439fd3377bf8ccdd746709bb6fc6fe71a014c528caea53
Tx public key: 0f7e0f935041ceaf24d5170518930c0dfe1aa4ad28e947b58ca5f0df19d42494
Timestamp: 1726434614 Timestamp [UCT]: 2024-09-15 21:10:14 Age [y:d:h:m:s]: 00:212:13:49:57
Block: 1110901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151765 RingCT/type: yes/0
Extra: 010f7e0f935041ceaf24d5170518930c0dfe1aa4ad28e947b58ca5f0df19d42494021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77b6e356f3ba76f23cb48bce9e874edf38defe5ef304749037aeebc07c468cc8 0.600000000000 1589674 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": 1110911, "vin": [ { "gen": { "height": 1110901 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77b6e356f3ba76f23cb48bce9e874edf38defe5ef304749037aeebc07c468cc8" } } ], "extra": [ 1, 15, 126, 15, 147, 80, 65, 206, 175, 36, 213, 23, 5, 24, 147, 12, 13, 254, 26, 164, 173, 40, 233, 71, 181, 140, 165, 240, 223, 25, 212, 36, 148, 2, 17, 0, 0, 0, 3, 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