Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 660a40d0e3a6976b75b46b467225e6a6501bb7efece99af245e3853e4d23594f

Tx prefix hash: 2323e15a37e850a47bd2038b9b399b541edd6f5795dffe06d530542656359f19
Tx public key: 676126bb419e0c02dd6d3ebde33e7a9eec70d812bb1c5f53e358dc080243f97d
Timestamp: 1694903045 Timestamp [UCT]: 2023-09-16 22:24:05 Age [y:d:h:m:s]: 01:116:07:08:06
Block: 849674 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344429 RingCT/type: yes/0
Extra: 01676126bb419e0c02dd6d3ebde33e7a9eec70d812bb1c5f53e358dc080243f97d021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.939025484000 dcy

stealth address amount amount idx
00: d68c46e349cf0c1d139e303a5581740b44d3353461fb7883343254c187e27060 0.939025484000 1303350 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": 849684, "vin": [ { "gen": { "height": 849674 } } ], "vout": [ { "amount": 939025484, "target": { "key": "d68c46e349cf0c1d139e303a5581740b44d3353461fb7883343254c187e27060" } } ], "extra": [ 1, 103, 97, 38, 187, 65, 158, 12, 2, 221, 109, 62, 189, 227, 62, 122, 158, 236, 112, 216, 18, 187, 28, 95, 83, 227, 88, 220, 8, 2, 67, 249, 125, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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