Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33d174ab4f699dc94c5e983f095aab1f26c86bb50e940d8b07beeab9592c5a30

Tx prefix hash: b4debe1aee0b589de414f77b21955dbbaaa71af7e19fbb787ed1461c785aa6bc
Tx public key: 9c9533ba5ed72908cc3733a1ee9f9726d2143717f00a5980f1b18a719a40661a
Timestamp: 1580480516 Timestamp [UCT]: 2020-01-31 14:21:56 Age [y:d:h:m:s]: 05:278:15:07:02
Block: 55821 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1348756 RingCT/type: yes/0
Extra: 019c9533ba5ed72908cc3733a1ee9f9726d2143717f00a5980f1b18a719a40661a0211000000012264afe6000000000000000000

1 output(s) for total of 400.906113599000 dcy

stealth address amount amount idx
00: 0f44da7c7573dd40708e5eaf3142888f90110aef3cbe6ccc153821e05816242e 400.906113599000 102988 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": 55831, "vin": [ { "gen": { "height": 55821 } } ], "vout": [ { "amount": 400906113599, "target": { "key": "0f44da7c7573dd40708e5eaf3142888f90110aef3cbe6ccc153821e05816242e" } } ], "extra": [ 1, 156, 149, 51, 186, 94, 215, 41, 8, 204, 55, 51, 161, 238, 159, 151, 38, 210, 20, 55, 23, 240, 10, 89, 128, 241, 177, 138, 113, 154, 64, 102, 26, 2, 17, 0, 0, 0, 1, 34, 100, 175, 230, 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