Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a8e29679a8cdafe7a7d09d3bbe14a1cf235279e574b5622713e1ec047e668c1

Tx prefix hash: 3dc7035931b20040e4a5def7ddfda85675038425ca84e76e90f5df823f223013
Tx public key: 880562b2537f0af5d2ed05e3c9a9a8197beccb5ce0d891ac371408c9eb762f30
Timestamp: 1724889894 Timestamp [UCT]: 2024-08-29 00:04:54 Age [y:d:h:m:s]: 00:229:00:04:11
Block: 1098089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163531 RingCT/type: yes/0
Extra: 01880562b2537f0af5d2ed05e3c9a9a8197beccb5ce0d891ac371408c9eb762f3002110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 050f0669f09d368a674e58aba83e1e03d23b8bf1c99847a67c35214d42f80643 0.600000000000 1573688 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": 1098099, "vin": [ { "gen": { "height": 1098089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "050f0669f09d368a674e58aba83e1e03d23b8bf1c99847a67c35214d42f80643" } } ], "extra": [ 1, 136, 5, 98, 178, 83, 127, 10, 245, 210, 237, 5, 227, 201, 169, 168, 25, 123, 236, 203, 92, 224, 216, 145, 172, 55, 20, 8, 201, 235, 118, 47, 48, 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