Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0667083d0f7979da4ed06ba6bc292383dbe1cf88fc676c06f176a20a4913584

Tx prefix hash: fdf30c3cd77f7ae844c98c1003b791725ab4aa0ea7c942c53d0cac64d1eab3cc
Tx public key: a08c67d72ba4c35bee0703c549e86465e3b27411b63b0402f4be50f35c57122f
Timestamp: 1714702770 Timestamp [UCT]: 2024-05-03 02:19:30 Age [y:d:h:m:s]: 00:318:02:38:58
Block: 1013650 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227392 RingCT/type: yes/0
Extra: 01a08c67d72ba4c35bee0703c549e86465e3b27411b63b0402f4be50f35c57122f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8142ebe802dc1e726f3bffd36b496627aeba0a3222737e7f5cfb577a54fe36f7 0.600000000000 1476521 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": 1013660, "vin": [ { "gen": { "height": 1013650 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8142ebe802dc1e726f3bffd36b496627aeba0a3222737e7f5cfb577a54fe36f7" } } ], "extra": [ 1, 160, 140, 103, 215, 43, 164, 195, 91, 238, 7, 3, 197, 73, 232, 100, 101, 227, 178, 116, 17, 182, 59, 4, 2, 244, 190, 80, 243, 92, 87, 18, 47, 2, 17, 0, 0, 0, 3, 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