Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eb291536044f65b5fc14c00c4e405de6b2d5539bba79e8b2db4e2f7508ba3eaf

Tx prefix hash: f5ff9d7bede3fcbb0b712299cb352a8f5dbce33f1c0d0df8e88e1eaf85fd783a
Tx public key: 0eeb671cd96b7f1e3635c44e1cc2a4637802f93d140d5bd7eebe5ce41ea9225a
Timestamp: 1733307089 Timestamp [UCT]: 2024-12-04 10:11:29 Age [y:d:h:m:s]: 00:124:03:24:04
Block: 1167776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88514 RingCT/type: yes/0
Extra: 010eeb671cd96b7f1e3635c44e1cc2a4637802f93d140d5bd7eebe5ce41ea9225a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cded17169aff113c5b84b0cf28f9eb8c0e05e8db4bc3426c8e80fa54b456db4 0.600000000000 1653479 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": 1167786, "vin": [ { "gen": { "height": 1167776 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cded17169aff113c5b84b0cf28f9eb8c0e05e8db4bc3426c8e80fa54b456db4" } } ], "extra": [ 1, 14, 235, 103, 28, 217, 107, 127, 30, 54, 53, 196, 78, 28, 194, 164, 99, 120, 2, 249, 61, 20, 13, 91, 215, 238, 190, 92, 228, 30, 169, 34, 90, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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