Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3fc32448c3f0e76a7027db2ae32a41dc121b7c518c620471345dfe367f886f41

Tx prefix hash: 607e95987cb92a2f25019f75f4547493e127380d721b5db7d37090a1ec71f154
Tx public key: 3045a804690d0264ca1d6e62f4e49900c279d12a81de31504e2f13bf372dc89c
Timestamp: 1581090501 Timestamp [UCT]: 2020-02-07 15:48:21 Age [y:d:h:m:s]: 05:031:07:49:48
Block: 60647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1174506 RingCT/type: yes/0
Extra: 013045a804690d0264ca1d6e62f4e49900c279d12a81de31504e2f13bf372dc89c021100000001026b59f3000000000000000000

1 output(s) for total of 386.413357467000 dcy

stealth address amount amount idx
00: 889a3ce584b70cc3dcf277fb1e20c946b503ac28f096b1d6563707da45579dca 386.413357467000 111680 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": 60657, "vin": [ { "gen": { "height": 60647 } } ], "vout": [ { "amount": 386413357467, "target": { "key": "889a3ce584b70cc3dcf277fb1e20c946b503ac28f096b1d6563707da45579dca" } } ], "extra": [ 1, 48, 69, 168, 4, 105, 13, 2, 100, 202, 29, 110, 98, 244, 228, 153, 0, 194, 121, 209, 42, 129, 222, 49, 80, 78, 47, 19, 191, 55, 45, 200, 156, 2, 17, 0, 0, 0, 1, 2, 107, 89, 243, 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