Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 946828500a9a066752a443afb6795f382e2472bd341c6be8c999327328b56b58

Tx prefix hash: a2bcea8ba8b4119e182f3a2d7ebf1f93bcbf995badf732040c2a75ad8dc1e2f5
Tx public key: 91fb0ca0e8db654dfbff8ec43664f599035fc4d15bb251d07d7ef9385282efea
Timestamp: 1626753480 Timestamp [UCT]: 2021-07-20 03:58:00 Age [y:d:h:m:s]: 03:171:07:27:22
Block: 297340 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 894092 RingCT/type: yes/0
Extra: 0191fb0ca0e8db654dfbff8ec43664f599035fc4d15bb251d07d7ef9385282efea021100000010d142c209000000000000000000

1 output(s) for total of 63.502327391000 dcy

stealth address amount amount idx
00: d5bb2a53bfa7699329844c062a2ae88e1ec4a6030fdb7cc1f9c53dc3cb401b8f 63.502327391000 622334 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": 297350, "vin": [ { "gen": { "height": 297340 } } ], "vout": [ { "amount": 63502327391, "target": { "key": "d5bb2a53bfa7699329844c062a2ae88e1ec4a6030fdb7cc1f9c53dc3cb401b8f" } } ], "extra": [ 1, 145, 251, 12, 160, 232, 219, 101, 77, 251, 255, 142, 196, 54, 100, 245, 153, 3, 95, 196, 209, 91, 178, 81, 208, 125, 126, 249, 56, 82, 130, 239, 234, 2, 17, 0, 0, 0, 16, 209, 66, 194, 9, 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