Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4e7d8f41a300599f0fa765629be8c21a4177908c7c6ac5754627bd88a174e6d

Tx prefix hash: ee8227e2f1de50f4015468197656e66eaf0113e9c03745f096706161841e0af1
Tx public key: fb83de046a32f8bc2761ae32d3a90db9372df949a313fd0c657158e4dc9081a8
Timestamp: 1710570749 Timestamp [UCT]: 2024-03-16 06:32:29 Age [y:d:h:m:s]: 01:014:21:31:59
Block: 979407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271596 RingCT/type: yes/0
Extra: 01fb83de046a32f8bc2761ae32d3a90db9372df949a313fd0c657158e4dc9081a802110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 278732b9c4b8cc2a82aab837d26c290e1ce5dc2f83d71b7370dc50bf569dad96 0.600000000000 1439440 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": 979417, "vin": [ { "gen": { "height": 979407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "278732b9c4b8cc2a82aab837d26c290e1ce5dc2f83d71b7370dc50bf569dad96" } } ], "extra": [ 1, 251, 131, 222, 4, 106, 50, 248, 188, 39, 97, 174, 50, 211, 169, 13, 185, 55, 45, 249, 73, 163, 19, 253, 12, 101, 113, 88, 228, 220, 144, 129, 168, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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