Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 869e25d4b773bfde16faa242e02d1a9ab1b62735d1df1988e914c340e3308952

Tx prefix hash: 1e74c705793718d33aaf3f1a511845edb91924a45894559c79b5e93c1a515531
Tx public key: fb67f7143caf7ef91b40a646b22b46710fa99cf6e3af8d12f5ae314f5421e741
Timestamp: 1706719001 Timestamp [UCT]: 2024-01-31 16:36:41 Age [y:d:h:m:s]: 00:288:11:48:50
Block: 947425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206574 RingCT/type: yes/0
Extra: 01fb67f7143caf7ef91b40a646b22b46710fa99cf6e3af8d12f5ae314f5421e74102110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 578a09c97a5a72bf2e006f5cdedebbb4f3e37eff37e413d5481e83b07275410b 0.600000000000 1405773 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": 947435, "vin": [ { "gen": { "height": 947425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "578a09c97a5a72bf2e006f5cdedebbb4f3e37eff37e413d5481e83b07275410b" } } ], "extra": [ 1, 251, 103, 247, 20, 60, 175, 126, 249, 27, 64, 166, 70, 178, 43, 70, 113, 15, 169, 156, 246, 227, 175, 141, 18, 245, 174, 49, 79, 84, 33, 231, 65, 2, 17, 0, 0, 0, 5, 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