Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a19a8468c93696dad1dc92ddcc673bfc1cf3076a14b8e6ff4af10710c4a22dc8

Tx prefix hash: a432ee1e5a193e722fb203c4da7d59a820a7bff0bcc4460fd7ccfc1feda707ea
Tx public key: a9e8665f61554d6673c8677314ab979028f66e05cd73f7b9f1fcfe1d576860f8
Timestamp: 1659153435 Timestamp [UCT]: 2022-07-30 03:57:15 Age [y:d:h:m:s]: 02:240:14:38:14
Block: 554705 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 693144 RingCT/type: yes/0
Extra: 01a9e8665f61554d6673c8677314ab979028f66e05cd73f7b9f1fcfe1d576860f802110000000175e3f0e9000000000000000000

1 output(s) for total of 8.913170031000 dcy

stealth address amount amount idx
00: 2c7be54d24b9406fb3abe44d4241e447d91d37e59b3a6e8ae0cb567fb9d29b95 8.913170031000 986563 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": 554715, "vin": [ { "gen": { "height": 554705 } } ], "vout": [ { "amount": 8913170031, "target": { "key": "2c7be54d24b9406fb3abe44d4241e447d91d37e59b3a6e8ae0cb567fb9d29b95" } } ], "extra": [ 1, 169, 232, 102, 95, 97, 85, 77, 102, 115, 200, 103, 115, 20, 171, 151, 144, 40, 246, 110, 5, 205, 115, 247, 185, 241, 252, 254, 29, 87, 104, 96, 248, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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