Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d2a4dd81e7a310d9e304d223ad821d58c730a46fc28a42409e52e15205f7e29

Tx prefix hash: 32d8fb4d5ccb335cdb989de12069373ebf9c0fa1213ef9608456c9055846d91f
Tx public key: 1de6b7cbdc292bee2414b628c1ddf5eb8e17fd435f1202622f625f1364b59b7c
Timestamp: 1577957630 Timestamp [UCT]: 2020-01-02 09:33:50 Age [y:d:h:m:s]: 05:001:06:20:02
Block: 37090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150882 RingCT/type: yes/0
Extra: 011de6b7cbdc292bee2414b628c1ddf5eb8e17fd435f1202622f625f1364b59b7c0211000000034943cd9f000000000000000000

1 output(s) for total of 462.494193986000 dcy

stealth address amount amount idx
00: 530278917af60ff8360204cf12d42966de6f384ffaf20352932292a49ec1b5a6 462.494193986000 62896 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": 37100, "vin": [ { "gen": { "height": 37090 } } ], "vout": [ { "amount": 462494193986, "target": { "key": "530278917af60ff8360204cf12d42966de6f384ffaf20352932292a49ec1b5a6" } } ], "extra": [ 1, 29, 230, 183, 203, 220, 41, 43, 238, 36, 20, 182, 40, 193, 221, 245, 235, 142, 23, 253, 67, 95, 18, 2, 98, 47, 98, 95, 19, 100, 181, 155, 124, 2, 17, 0, 0, 0, 3, 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