Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e147a2bb72f07cbb405ffbe8f41c73dcdf25e7aea30bb822443cdd768a847140

Tx prefix hash: 83c1f65343bc492c1565c3366c258c8c94cb7c0e6e2d5dc518af52deb1e96864
Tx public key: e52ae830d2958faa5d0f8faf50d50897e8c9dcbfc22db48218a6bdec12ddd747
Timestamp: 1696821736 Timestamp [UCT]: 2023-10-09 03:22:16 Age [y:d:h:m:s]: 01:181:01:52:33
Block: 865601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 390436 RingCT/type: yes/0
Extra: 01e52ae830d2958faa5d0f8faf50d50897e8c9dcbfc22db48218a6bdec12ddd74702110000000875e3f0e9000000000000000000

1 output(s) for total of 0.831581066000 dcy

stealth address amount amount idx
00: adcb56db591517c3fac20dbedc92a413c24e2fd570c1d6029f3ae1f898f38a50 0.831581066000 1320139 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": 865611, "vin": [ { "gen": { "height": 865601 } } ], "vout": [ { "amount": 831581066, "target": { "key": "adcb56db591517c3fac20dbedc92a413c24e2fd570c1d6029f3ae1f898f38a50" } } ], "extra": [ 1, 229, 42, 232, 48, 210, 149, 143, 170, 93, 15, 143, 175, 80, 213, 8, 151, 232, 201, 220, 191, 194, 45, 180, 130, 24, 166, 189, 236, 18, 221, 215, 71, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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