Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7d03f6dd0372cfb88a9c8fc078f16fbac24b0ecab408a5e49a61980d44296c2

Tx prefix hash: 2937687c19f21e67e0f136f57c257ec5e2be0b90c1fb7e2235c0501c13dd5bd9
Tx public key: 6a96744e5345b0d605350c1b838728518c3c18abb6e07ef572ceccdb31ac167a
Timestamp: 1578322766 Timestamp [UCT]: 2020-01-06 14:59:26 Age [y:d:h:m:s]: 05:011:22:21:03
Block: 39748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1158879 RingCT/type: yes/0
Extra: 016a96744e5345b0d605350c1b838728518c3c18abb6e07ef572ceccdb31ac167a021100000093391a8d0e000000000000000000

1 output(s) for total of 453.209728565000 dcy

stealth address amount amount idx
00: ba4c53f0e33da6f842cbce401fa535232d451281b090495739f2b5c50d65e1b3 453.209728565000 69011 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": 39758, "vin": [ { "gen": { "height": 39748 } } ], "vout": [ { "amount": 453209728565, "target": { "key": "ba4c53f0e33da6f842cbce401fa535232d451281b090495739f2b5c50d65e1b3" } } ], "extra": [ 1, 106, 150, 116, 78, 83, 69, 176, 214, 5, 53, 12, 27, 131, 135, 40, 81, 140, 60, 24, 171, 182, 224, 126, 245, 114, 206, 204, 219, 49, 172, 22, 122, 2, 17, 0, 0, 0, 147, 57, 26, 141, 14, 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