Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5826a4f0fd69f6e28a32f1eecad0a2ef710fe1562f902665a8f8aa9c42f396a3

Tx prefix hash: 432c23f5dbd233ec93118066b8dbb7ee2266e29d35f90d254b090c6739c569e2
Tx public key: ae71a362e1e309fc3d9a33197e972ec2956832dd4e9be74e68027f3bd6dc10ec
Timestamp: 1712673898 Timestamp [UCT]: 2024-04-09 14:44:58 Age [y:d:h:m:s]: 01:071:14:51:45
Block: 996794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312067 RingCT/type: yes/0
Extra: 01ae71a362e1e309fc3d9a33197e972ec2956832dd4e9be74e68027f3bd6dc10ec02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c62b87d8a3c93f94ad3f96d4ad84db7f24690bab8b1f215f406da98aac84fce 0.600000000000 1457222 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": 996804, "vin": [ { "gen": { "height": 996794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c62b87d8a3c93f94ad3f96d4ad84db7f24690bab8b1f215f406da98aac84fce" } } ], "extra": [ 1, 174, 113, 163, 98, 225, 227, 9, 252, 61, 154, 51, 25, 126, 151, 46, 194, 149, 104, 50, 221, 78, 155, 231, 78, 104, 2, 127, 59, 214, 220, 16, 236, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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