Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: defb0779203c75a4ed54292278a3f7d9c7a43200cf80d0249c0a14249d895474

Tx prefix hash: 42cf6d59910f87385eeddc2b79f914a7e3ebaac5d5354b56c3e210c1bec7e015
Tx public key: 38ffabc31c5f1c458c04f57f7112d7174309b4e93d99eb80b76d0562614acd19
Timestamp: 1728325834 Timestamp [UCT]: 2024-10-07 18:30:34 Age [y:d:h:m:s]: 00:187:13:35:13
Block: 1126578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133852 RingCT/type: yes/0
Extra: 0138ffabc31c5f1c458c04f57f7112d7174309b4e93d99eb80b76d0562614acd1902110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf9ace08afdf54b6b000c938400b943ad9acf9f69674028cda5d49339ae58cd7 0.600000000000 1609373 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": 1126588, "vin": [ { "gen": { "height": 1126578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf9ace08afdf54b6b000c938400b943ad9acf9f69674028cda5d49339ae58cd7" } } ], "extra": [ 1, 56, 255, 171, 195, 28, 95, 28, 69, 140, 4, 245, 127, 113, 18, 215, 23, 67, 9, 180, 233, 61, 153, 235, 128, 183, 109, 5, 98, 97, 74, 205, 25, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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