Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 321620f08bc86c60801313b0c3b466f1979c1a823961088cffa6c429251e9c4c

Tx prefix hash: af7383acd69560fd718ea7e1ca51c99153c652d097424945c82b9766d7cc4868
Tx public key: 8ae853646bdd38ee34164041125bd44b5b62ed6b6f2bbf0d3d61f9d6f6cd9642
Timestamp: 1724218891 Timestamp [UCT]: 2024-08-21 05:41:31 Age [y:d:h:m:s]: 00:224:18:03:24
Block: 1092542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160475 RingCT/type: yes/0
Extra: 018ae853646bdd38ee34164041125bd44b5b62ed6b6f2bbf0d3d61f9d6f6cd964202110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 81aa0515370aa058c552431c0ead282f827ee2e55a2a79b401873cad36237ad9 0.600000000000 1567309 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": 1092552, "vin": [ { "gen": { "height": 1092542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "81aa0515370aa058c552431c0ead282f827ee2e55a2a79b401873cad36237ad9" } } ], "extra": [ 1, 138, 232, 83, 100, 107, 221, 56, 238, 52, 22, 64, 65, 18, 91, 212, 75, 91, 98, 237, 107, 111, 43, 191, 13, 61, 97, 249, 214, 246, 205, 150, 66, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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