Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ef7aefa20480e637d77ec73e8f27ddbae74c2fbdd099f3481ebf07a494f76a

Tx prefix hash: d8acef0c0d66bb79e61ffbbbf184338ba1a1b412722311d733bb4eea9eff1420
Tx public key: 39d4952f965c6f58d3cc210a7ccf65be75f1c8773fa1d33a03e164d7aa33b245
Timestamp: 1712448813 Timestamp [UCT]: 2024-04-07 00:13:33 Age [y:d:h:m:s]: 00:364:16:54:44
Block: 994921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260758 RingCT/type: yes/0
Extra: 0139d4952f965c6f58d3cc210a7ccf65be75f1c8773fa1d33a03e164d7aa33b24502110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82bf992dc3d505ebe0f90a12809d955644832c685e5feaef22dc177d7452ea79 0.600000000000 1455325 of 15

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": 994931, "vin": [ { "gen": { "height": 994921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82bf992dc3d505ebe0f90a12809d955644832c685e5feaef22dc177d7452ea79" } } ], "extra": [ 1, 57, 212, 149, 47, 150, 92, 111, 88, 211, 204, 33, 10, 124, 207, 101, 190, 117, 241, 200, 119, 63, 161, 211, 58, 3, 225, 100, 215, 170, 51, 178, 69, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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