Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf5aede354a65f8c75be4eaeb99a853b6313edfd95a5dc600a01efb623ca7bd0

Tx prefix hash: 03057393549134e0c1e84a66237687384f2824cd5e15ab62c3faf0d0d1d6af5f
Tx public key: 97a918afdb025aafe1fa91db05e81df4db051aed14410c23ab68da12ee07ec0a
Timestamp: 1648723799 Timestamp [UCT]: 2022-03-31 10:49:59 Age [y:d:h:m:s]: 02:349:04:26:03
Block: 470248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 768955 RingCT/type: yes/0
Extra: 0197a918afdb025aafe1fa91db05e81df4db051aed14410c23ab68da12ee07ec0a0211000000275eb576c5000000000000000000

1 output(s) for total of 16.977487363000 dcy

stealth address amount amount idx
00: fa3f7fb0b792193843dc4519689f6da1aa2b639b6e77c577f1b820159c149ba6 16.977487363000 889362 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": 470258, "vin": [ { "gen": { "height": 470248 } } ], "vout": [ { "amount": 16977487363, "target": { "key": "fa3f7fb0b792193843dc4519689f6da1aa2b639b6e77c577f1b820159c149ba6" } } ], "extra": [ 1, 151, 169, 24, 175, 219, 2, 90, 175, 225, 250, 145, 219, 5, 232, 29, 244, 219, 5, 26, 237, 20, 65, 12, 35, 171, 104, 218, 18, 238, 7, 236, 10, 2, 17, 0, 0, 0, 39, 94, 181, 118, 197, 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