Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 796ef9adc4d791134d23e64d616ca899f6026ac16ebf36675905e11200478899

Tx prefix hash: dd05e609983e0f7c1ac21f3c224904f914e5f21b5902ee096e39c3d00a89dcc1
Tx public key: 562c675f51e55e05800623ffab2642cb04c4e14dafda14b1f4869ed0279c4837
Timestamp: 1580781401 Timestamp [UCT]: 2020-02-04 01:56:41 Age [y:d:h:m:s]: 05:294:08:37:39
Block: 57977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1360348 RingCT/type: yes/0
Extra: 01562c675f51e55e05800623ffab2642cb04c4e14dafda14b1f4869ed0279c48370211000000184943cd9f000000000000000000

1 output(s) for total of 394.365534547000 dcy

stealth address amount amount idx
00: 725d4240d34beed3c124f11152736024d0cac35b3d94ea178307cf6f701a0fb5 394.365534547000 107236 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": 57987, "vin": [ { "gen": { "height": 57977 } } ], "vout": [ { "amount": 394365534547, "target": { "key": "725d4240d34beed3c124f11152736024d0cac35b3d94ea178307cf6f701a0fb5" } } ], "extra": [ 1, 86, 44, 103, 95, 81, 229, 94, 5, 128, 6, 35, 255, 171, 38, 66, 203, 4, 196, 225, 77, 175, 218, 20, 177, 244, 134, 158, 208, 39, 156, 72, 55, 2, 17, 0, 0, 0, 24, 73, 67, 205, 159, 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