Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa573f751f94edb11de5418fe5f630404030aac1e5c5efde5ca70ca31e01d7cc

Tx prefix hash: cdd56df44829916798d4f3feb360b93f838598545c4d998bfd3cda1748128e47
Tx public key: 62f024f0e0e27ecb69e68ca735d1f0bf65afe3009c1286aba5b3413e83da1f1d
Timestamp: 1702499807 Timestamp [UCT]: 2023-12-13 20:36:47 Age [y:d:h:m:s]: 01:038:21:13:51
Block: 912467 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289114 RingCT/type: yes/0
Extra: 0162f024f0e0e27ecb69e68ca735d1f0bf65afe3009c1286aba5b3413e83da1f1d021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 23c03f0b06b3913ad9ed1e54b8d406d12ec4a04bdecfb4acaa2c81a47887100d 0.600000000000 1369695 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": 912477, "vin": [ { "gen": { "height": 912467 } } ], "vout": [ { "amount": 600000000, "target": { "key": "23c03f0b06b3913ad9ed1e54b8d406d12ec4a04bdecfb4acaa2c81a47887100d" } } ], "extra": [ 1, 98, 240, 36, 240, 224, 226, 126, 203, 105, 230, 140, 167, 53, 209, 240, 191, 101, 175, 227, 0, 156, 18, 134, 171, 165, 179, 65, 62, 131, 218, 31, 29, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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