Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 047fa5faee494d38dbc150e9f8574adb4093fd9f940e03d6598c3236e57be5a9

Tx prefix hash: 0799c9cb8543f047ca430b7327d54ab9e0a797e679b263953b2feea1785cf689
Tx public key: 567f248943046369e27cdae38931aa3d2340ca55ac6c5a11775e658181cd993b
Timestamp: 1581090564 Timestamp [UCT]: 2020-02-07 15:49:24 Age [y:d:h:m:s]: 04:296:19:22:31
Block: 60656 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1103570 RingCT/type: yes/0
Extra: 01567f248943046369e27cdae38931aa3d2340ca55ac6c5a11775e658181cd993b02110000000e8a2ee0d9000000000000000000

1 output(s) for total of 386.386825377000 dcy

stealth address amount amount idx
00: 5863f7892cd5c943f399c33e76c26bab3a24b9fc4155f951e46644b5219aae69 386.386825377000 111689 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": 60666, "vin": [ { "gen": { "height": 60656 } } ], "vout": [ { "amount": 386386825377, "target": { "key": "5863f7892cd5c943f399c33e76c26bab3a24b9fc4155f951e46644b5219aae69" } } ], "extra": [ 1, 86, 127, 36, 137, 67, 4, 99, 105, 226, 124, 218, 227, 137, 49, 170, 61, 35, 64, 202, 85, 172, 108, 90, 17, 119, 94, 101, 129, 129, 205, 153, 59, 2, 17, 0, 0, 0, 14, 138, 46, 224, 217, 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