Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41afca91b1ecbab873cddf36d404f17c610ccfbfc8dcea3030a746a686ea1935

Tx prefix hash: 07315a7baddef94d00b970c10d79f999e5bb68fb35c7345ac0ab064abbbe0819
Tx public key: aa89f7b937ce3213a2903922eaa1c740b89e8df4c05e6f4228e4fe0a7d609065
Timestamp: 1740178532 Timestamp [UCT]: 2025-02-21 22:55:32 Age [y:d:h:m:s]: 00:279:07:56:34
Block: 1224377 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197423 RingCT/type: yes/0
Extra: 01aa89f7b937ce3213a2903922eaa1c740b89e8df4c05e6f4228e4fe0a7d6090650211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 74f60ec767841ed7830233c24a1c93b1fca18d40fb492c76f37317724d18f3ab 0.600000000000 1711236 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": 1224387, "vin": [ { "gen": { "height": 1224377 } } ], "vout": [ { "amount": 600000000, "target": { "key": "74f60ec767841ed7830233c24a1c93b1fca18d40fb492c76f37317724d18f3ab" } } ], "extra": [ 1, 170, 137, 247, 185, 55, 206, 50, 19, 162, 144, 57, 34, 234, 161, 199, 64, 184, 158, 141, 244, 192, 94, 111, 66, 40, 228, 254, 10, 125, 96, 144, 101, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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