Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9cde8af5f14762d0711447dc79be85d4161246f76304bcf3e2e984367c9b1be2

Tx prefix hash: 97024f3d7c0411c7f3c556618620c7ec185fdd33cfb0756ec224fa97b3cfe1f2
Tx public key: 5ed60fbd29dc4ef3a80a36ca73a102791a802b134b0f85ddbafda46eaacbba21
Timestamp: 1580708881 Timestamp [UCT]: 2020-02-03 05:48:01 Age [y:d:h:m:s]: 04:347:20:45:12
Block: 57793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1139796 RingCT/type: yes/0
Extra: 015ed60fbd29dc4ef3a80a36ca73a102791a802b134b0f85ddbafda46eaacbba2102110000000117786bcf000000000000000000

1 output(s) for total of 394.926359155000 dcy

stealth address amount amount idx
00: 3ea754cdbd29faccc098d64130cd5ab0704e67e4efa598fcd70114e7dd1a8cb7 394.926359155000 106817 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": 57803, "vin": [ { "gen": { "height": 57793 } } ], "vout": [ { "amount": 394926359155, "target": { "key": "3ea754cdbd29faccc098d64130cd5ab0704e67e4efa598fcd70114e7dd1a8cb7" } } ], "extra": [ 1, 94, 214, 15, 189, 41, 220, 78, 243, 168, 10, 54, 202, 115, 161, 2, 121, 26, 128, 43, 19, 75, 15, 133, 221, 186, 253, 164, 110, 170, 203, 186, 33, 2, 17, 0, 0, 0, 1, 23, 120, 107, 207, 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