Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a9de207ebe08bcf83d4460c04e082673f06ccc90acd12a80a68d8cb01f17e93

Tx prefix hash: ffa4f1ce507286fb66d789f70a9025cf1dae22795c8fe7e09cce4b127689ac5e
Tx public key: 1046dccce2674621a4faf64d530744ca9c26d737fa94a25a11d41923b9f86a88
Timestamp: 1638759187 Timestamp [UCT]: 2021-12-06 02:53:07 Age [y:d:h:m:s]: 03:330:20:47:32
Block: 389366 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1012897 RingCT/type: yes/0
Extra: 011046dccce2674621a4faf64d530744ca9c26d737fa94a25a11d41923b9f86a88021100000012d6e4826b000000000000000000

1 output(s) for total of 31.468002463000 dcy

stealth address amount amount idx
00: c3902c840646bd23dca53f06fa8cf498d3fdc1d401b5115fa1fe28ff2c0a2de7 31.468002463000 784493 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": 389376, "vin": [ { "gen": { "height": 389366 } } ], "vout": [ { "amount": 31468002463, "target": { "key": "c3902c840646bd23dca53f06fa8cf498d3fdc1d401b5115fa1fe28ff2c0a2de7" } } ], "extra": [ 1, 16, 70, 220, 204, 226, 103, 70, 33, 164, 250, 246, 77, 83, 7, 68, 202, 156, 38, 215, 55, 250, 148, 162, 90, 17, 212, 25, 35, 185, 248, 106, 136, 2, 17, 0, 0, 0, 18, 214, 228, 130, 107, 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