Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0d0983f853cc4fd266e5170cc04b5568ceda308826504c98a08726d2641f561

Tx prefix hash: 7f86ca43acc320c6ef6a674a0c4319a368275ba33ee34a83203730f65c2dc7d9
Tx public key: a6913bd821e9e7976801500f6420eeed8d214bc257a7fab87d69edd5cac3d5d6
Timestamp: 1702209221 Timestamp [UCT]: 2023-12-10 11:53:41 Age [y:d:h:m:s]: 01:333:12:15:45
Block: 910066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497215 RingCT/type: yes/0
Extra: 01a6913bd821e9e7976801500f6420eeed8d214bc257a7fab87d69edd5cac3d5d60211000000064b8f5122000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd39397835e29f2f396bc519a6dbacad7fdcf3831a52a03a1de137e5888c3bb1 0.600000000000 1367207 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": 910076, "vin": [ { "gen": { "height": 910066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd39397835e29f2f396bc519a6dbacad7fdcf3831a52a03a1de137e5888c3bb1" } } ], "extra": [ 1, 166, 145, 59, 216, 33, 233, 231, 151, 104, 1, 80, 15, 100, 32, 238, 237, 141, 33, 75, 194, 87, 167, 250, 184, 125, 105, 237, 213, 202, 195, 213, 214, 2, 17, 0, 0, 0, 6, 75, 143, 81, 34, 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