Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b075cbd60ca833c6fa4bb3af07b943b0a5d24eb4a3a814a5dc32eec9eb240ba

Tx prefix hash: 43a1f00129d0e14766af5167feb04b4e4afeb6985e396ea8122bc67cad479486
Tx public key: b4b8d0d948a0f5be1bf042a26c1611468a23021450e114a70b193893340e0bee
Timestamp: 1702560751 Timestamp [UCT]: 2023-12-14 13:32:31 Age [y:d:h:m:s]: 01:037:08:08:39
Block: 912972 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288012 RingCT/type: yes/0
Extra: 01b4b8d0d948a0f5be1bf042a26c1611468a23021450e114a70b193893340e0bee021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 939fda7228af89e66aa3885bf01f2c87adc0d5425cd2bede5657e6e22d1b7580 0.600000000000 1370210 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": 912982, "vin": [ { "gen": { "height": 912972 } } ], "vout": [ { "amount": 600000000, "target": { "key": "939fda7228af89e66aa3885bf01f2c87adc0d5425cd2bede5657e6e22d1b7580" } } ], "extra": [ 1, 180, 184, 208, 217, 72, 160, 245, 190, 27, 240, 66, 162, 108, 22, 17, 70, 138, 35, 2, 20, 80, 225, 20, 167, 11, 25, 56, 147, 52, 14, 11, 238, 2, 17, 0, 0, 0, 5, 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