Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67fb3979b9a1a815071789c3ec67adcddda1c55b2d073b2c875240a98e028d8b

Tx prefix hash: 90ec55f2a11201fffbdee3f139bbc1fef19dfadd51cc22c4925f1e6e9c20944c
Tx public key: 0361f09a3a78b404b8abebc1f098208ee71993d965eec07def8a8ff93c14cba8
Timestamp: 1709429146 Timestamp [UCT]: 2024-03-03 01:25:46 Age [y:d:h:m:s]: 01:015:07:33:12
Block: 969917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271953 RingCT/type: yes/0
Extra: 010361f09a3a78b404b8abebc1f098208ee71993d965eec07def8a8ff93c14cba80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0c60a8ffdbb99e981f9124b424231d1ffa1d68a26cf74030b43f9a8a3bca8a8 0.600000000000 1429766 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": 969927, "vin": [ { "gen": { "height": 969917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0c60a8ffdbb99e981f9124b424231d1ffa1d68a26cf74030b43f9a8a3bca8a8" } } ], "extra": [ 1, 3, 97, 240, 154, 58, 120, 180, 4, 184, 171, 235, 193, 240, 152, 32, 142, 231, 25, 147, 217, 101, 238, 192, 125, 239, 138, 143, 249, 60, 20, 203, 168, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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