Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 497e3ac54054ec0f81841b4af97648e67aa4ea2a302e5c3c38ca7a44b093ab90

Tx prefix hash: 6a03dc20f522e394bb008814a91b94fa811a0ff3764a2cfcb0c9b3e9c30a7d7a
Tx public key: ae40aa3e65f44017328db78415743dcc28ab41f18e87c70a656881bd91651ced
Timestamp: 1621567777 Timestamp [UCT]: 2021-05-21 03:29:37 Age [y:d:h:m:s]: 03:331:12:44:28
Block: 264357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 998466 RingCT/type: yes/0
Extra: 01ae40aa3e65f44017328db78415743dcc28ab41f18e87c70a656881bd91651ced02110000000f23fdb90b000000000000000000

1 output(s) for total of 81.673959799000 dcy

stealth address amount amount idx
00: 88de56abd4a187fdbdd832a5f10ce1d76469a2e532fc217c6050a36f3060600d 81.673959799000 555897 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": 264367, "vin": [ { "gen": { "height": 264357 } } ], "vout": [ { "amount": 81673959799, "target": { "key": "88de56abd4a187fdbdd832a5f10ce1d76469a2e532fc217c6050a36f3060600d" } } ], "extra": [ 1, 174, 64, 170, 62, 101, 244, 64, 23, 50, 141, 183, 132, 21, 116, 61, 204, 40, 171, 65, 241, 142, 135, 199, 10, 101, 104, 129, 189, 145, 101, 28, 237, 2, 17, 0, 0, 0, 15, 35, 253, 185, 11, 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