Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae3fc5c6071f3c7690941169607587f5ed601fcfd2237dfc3af74ea78cfc0f6

Tx prefix hash: 478b4714d55bd607bd2de281e314065b4f268bfe1bd22583524746ccb36e59c1
Tx public key: 39f177e55451cb945a57c958fa83e46765edcc6d1cdc57ff973db7dc21a01305
Timestamp: 1632362276 Timestamp [UCT]: 2021-09-23 01:57:56 Age [y:d:h:m:s]: 03:165:16:33:25
Block: 339157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 894411 RingCT/type: yes/0
Extra: 0139f177e55451cb945a57c958fa83e46765edcc6d1cdc57ff973db7dc21a01305021100000013f29d7abf000000000000000000

1 output(s) for total of 46.156460923000 dcy

stealth address amount amount idx
00: 95b4af653c9ad25be60c0edb03381c2f6a7123b6fe815a2fbce49d58e1f40f1d 46.156460923000 697660 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": 339167, "vin": [ { "gen": { "height": 339157 } } ], "vout": [ { "amount": 46156460923, "target": { "key": "95b4af653c9ad25be60c0edb03381c2f6a7123b6fe815a2fbce49d58e1f40f1d" } } ], "extra": [ 1, 57, 241, 119, 229, 84, 81, 203, 148, 90, 87, 201, 88, 250, 131, 228, 103, 101, 237, 204, 109, 28, 220, 87, 255, 151, 61, 183, 220, 33, 160, 19, 5, 2, 17, 0, 0, 0, 19, 242, 157, 122, 191, 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