Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab11f882f77e22da0f60bb417b87a3d3beb5aab636d56a29697483963ff00c4

Tx prefix hash: 02f8e8ef2e5aa2f55686d3bb4c7a08c7508e45752a225b37f87078f7137ae613
Tx public key: e2120e627bc27d179890957c55748881759f59402bf9515bf8298d894a3a485e
Timestamp: 1585242184 Timestamp [UCT]: 2020-03-26 17:03:04 Age [y:d:h:m:s]: 04:245:17:19:46
Block: 88508 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1073539 RingCT/type: yes/0
Extra: 01e2120e627bc27d179890957c55748881759f59402bf9515bf8298d894a3a485e02110000000139be35fb000000000000000000

1 output(s) for total of 312.418708010000 dcy

stealth address amount amount idx
00: cf8bade38bbce2de2570c88a6a37b4f9aa8a5c0f1f14ec9fe1f5cdd6a3fdec47 312.418708010000 159070 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": 88518, "vin": [ { "gen": { "height": 88508 } } ], "vout": [ { "amount": 312418708010, "target": { "key": "cf8bade38bbce2de2570c88a6a37b4f9aa8a5c0f1f14ec9fe1f5cdd6a3fdec47" } } ], "extra": [ 1, 226, 18, 14, 98, 123, 194, 125, 23, 152, 144, 149, 124, 85, 116, 136, 129, 117, 159, 89, 64, 43, 249, 81, 91, 248, 41, 141, 137, 74, 58, 72, 94, 2, 17, 0, 0, 0, 1, 57, 190, 53, 251, 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