Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07028097582703b091d807e95dc572b47f216e6a01dcdd48258dcfdf484fea7b

Tx prefix hash: 58740ad5668157cf670e57927e5307cc97c9e5c3235f981cb852c0c361b3e59b
Tx public key: b3df522d3e152f0a93ee305e9c64100ca474d7ee68350d8e7f28b7f94e122dc7
Timestamp: 1576425931 Timestamp [UCT]: 2019-12-15 16:05:31 Age [y:d:h:m:s]: 05:018:15:17:43
Block: 27666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1160050 RingCT/type: yes/0
Extra: 01b3df522d3e152f0a93ee305e9c64100ca474d7ee68350d8e7f28b7f94e122dc702110000002d9159db1e000000000000000000

1 output(s) for total of 496.972002577000 dcy

stealth address amount amount idx
00: 804cbbd88179e8b39c03a0a949ff4cdee3e809f616e7ea96a1f3ae2a642aecb8 496.972002577000 45702 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": 27676, "vin": [ { "gen": { "height": 27666 } } ], "vout": [ { "amount": 496972002577, "target": { "key": "804cbbd88179e8b39c03a0a949ff4cdee3e809f616e7ea96a1f3ae2a642aecb8" } } ], "extra": [ 1, 179, 223, 82, 45, 62, 21, 47, 10, 147, 238, 48, 94, 156, 100, 16, 12, 164, 116, 215, 238, 104, 53, 13, 142, 127, 40, 183, 249, 78, 18, 45, 199, 2, 17, 0, 0, 0, 45, 145, 89, 219, 30, 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