Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee41e8f718ff386e0819c1378d67074e985542998a75c5c98fe19bd150500459

Tx prefix hash: 500009ae16aa54de3733cc5e64fd0f0b4c462359ee5db2efdabb941ad88edbde
Tx public key: ad397fd7e2eb9f8b2e3e01e8494ae3f5b290025443494ede1267db72b6d17fbe
Timestamp: 1580699362 Timestamp [UCT]: 2020-02-03 03:09:22 Age [y:d:h:m:s]: 05:002:08:37:43
Block: 57573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153605 RingCT/type: yes/0
Extra: 01ad397fd7e2eb9f8b2e3e01e8494ae3f5b290025443494ede1267db72b6d17fbe021100000004bd0f9f9f000000000000000000

1 output(s) for total of 395.600257626000 dcy

stealth address amount amount idx
00: 6e0cfe34ab1a93d1283335d5386a7133e160794764de2cfa5b1bbad013ebc85a 395.600257626000 106417 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": 57583, "vin": [ { "gen": { "height": 57573 } } ], "vout": [ { "amount": 395600257626, "target": { "key": "6e0cfe34ab1a93d1283335d5386a7133e160794764de2cfa5b1bbad013ebc85a" } } ], "extra": [ 1, 173, 57, 127, 215, 226, 235, 159, 139, 46, 62, 1, 232, 73, 74, 227, 245, 178, 144, 2, 84, 67, 73, 78, 222, 18, 103, 219, 114, 182, 209, 127, 190, 2, 17, 0, 0, 0, 4, 189, 15, 159, 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