Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3547c5f2e406a4b0017d29b3fb7a778b1e36fc341aa9d30c254f14082a75a103

Tx prefix hash: 94c8b0721dcf99d64e4c77c020afc6af84cb901bc13a13a4344ab96d9fe9754e
Tx public key: 613cb09f8febb91d1e92050afafd1c7bacac0dc46377a0386c09fca316100f16
Timestamp: 1717588159 Timestamp [UCT]: 2024-06-05 11:49:19 Age [y:d:h:m:s]: 00:345:18:52:01
Block: 1037564 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 247146 RingCT/type: yes/0
Extra: 01613cb09f8febb91d1e92050afafd1c7bacac0dc46377a0386c09fca316100f160211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d42b600a2cc60982d35e32d9cc90b0b762cf4a784aa3a8a75705d40fd7fcf82 0.600000000000 1506109 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": 1037574, "vin": [ { "gen": { "height": 1037564 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d42b600a2cc60982d35e32d9cc90b0b762cf4a784aa3a8a75705d40fd7fcf82" } } ], "extra": [ 1, 97, 60, 176, 159, 143, 235, 185, 29, 30, 146, 5, 10, 250, 253, 28, 123, 172, 172, 13, 196, 99, 119, 160, 56, 108, 9, 252, 163, 22, 16, 15, 22, 2, 17, 0, 0, 0, 4, 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