Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efd2c640dcb9e87c1f70a5cd9d1c1e8f34a29d2bd9c1be3fa48878ec31879e89

Tx prefix hash: ff965a534b2ace049b5d35ea8344e76ca29f41a2dd5bd8e308a8493981961cd9
Tx public key: 444a9447f7610b1e386275b5448c173422dfafb05f85846c39c4282659cbdd2a
Timestamp: 1670936191 Timestamp [UCT]: 2022-12-13 12:56:31 Age [y:d:h:m:s]: 02:164:14:51:36
Block: 651688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 639379 RingCT/type: yes/0
Extra: 01444a9447f7610b1e386275b5448c173422dfafb05f85846c39c4282659cbdd2a0211000000067e406890000000000000000000

1 output(s) for total of 4.252919002000 dcy

stealth address amount amount idx
00: 0cf42cda815fd3de37591456e517bb1b9fbd4a408ff619b741d36daa3e0d4200 4.252919002000 1092105 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": 651698, "vin": [ { "gen": { "height": 651688 } } ], "vout": [ { "amount": 4252919002, "target": { "key": "0cf42cda815fd3de37591456e517bb1b9fbd4a408ff619b741d36daa3e0d4200" } } ], "extra": [ 1, 68, 74, 148, 71, 247, 97, 11, 30, 56, 98, 117, 181, 68, 140, 23, 52, 34, 223, 175, 176, 95, 133, 132, 108, 57, 196, 40, 38, 89, 203, 221, 42, 2, 17, 0, 0, 0, 6, 126, 64, 104, 144, 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