Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dab6687a87cce4ede3ba351fb703515154969c52aafab1c95d6ed35f309e9d1d

Tx prefix hash: ee1bad5deb254ec121a41cf84325056f4f179d684f3efb239f51e93056bfce14
Tx public key: 84e519da4e1f4ca5d37ec4990d470a4cb897d00d497d34e6dc339d3f71d305b5
Timestamp: 1583237949 Timestamp [UCT]: 2020-03-03 12:19:09 Age [y:d:h:m:s]: 04:335:13:32:28
Block: 75551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133909 RingCT/type: yes/0
Extra: 0184e519da4e1f4ca5d37ec4990d470a4cb897d00d497d34e6dc339d3f71d305b502110000020e026b59f3000000000000000000

1 output(s) for total of 344.880763072000 dcy

stealth address amount amount idx
00: 3b0b5f7f303d704f09313d4d202186e15f53d3deb2e6e4fe7a7cb0016dea6327 344.880763072000 139503 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": 75561, "vin": [ { "gen": { "height": 75551 } } ], "vout": [ { "amount": 344880763072, "target": { "key": "3b0b5f7f303d704f09313d4d202186e15f53d3deb2e6e4fe7a7cb0016dea6327" } } ], "extra": [ 1, 132, 229, 25, 218, 78, 31, 76, 165, 211, 126, 196, 153, 13, 71, 10, 76, 184, 151, 208, 13, 73, 125, 52, 230, 220, 51, 157, 63, 113, 211, 5, 181, 2, 17, 0, 0, 2, 14, 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