Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 095d3ae9a7398431c6d08d704ee495a9c955d3173b1cf492108dd65a849a2b60

Tx prefix hash: 70218ec44aa4fc8ebe8ab911a612b170a9ae4f42241e0f75d8cbeec174c5f9d1
Tx public key: 357b00a0bcfb860533e1b20902ec0352fe222a92cc71e1b23f02e08d3c958aab
Timestamp: 1632791121 Timestamp [UCT]: 2021-09-28 01:05:21 Age [y:d:h:m:s]: 03:230:05:01:10
Block: 342175 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 941094 RingCT/type: yes/0
Extra: 01357b00a0bcfb860533e1b20902ec0352fe222a92cc71e1b23f02e08d3c958aab021100000008a272b9cb000000000000000000

1 output(s) for total of 45.108123164000 dcy

stealth address amount amount idx
00: fe16df6f9a83821a5e7b6223c30226349edbd6ff3f425e1c6492e60fd3c025ae 45.108123164000 702747 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": 342185, "vin": [ { "gen": { "height": 342175 } } ], "vout": [ { "amount": 45108123164, "target": { "key": "fe16df6f9a83821a5e7b6223c30226349edbd6ff3f425e1c6492e60fd3c025ae" } } ], "extra": [ 1, 53, 123, 0, 160, 188, 251, 134, 5, 51, 225, 178, 9, 2, 236, 3, 82, 254, 34, 42, 146, 204, 113, 225, 178, 63, 2, 224, 141, 60, 149, 138, 171, 2, 17, 0, 0, 0, 8, 162, 114, 185, 203, 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