Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3afd5ec9e872f9252fff04c20bf2fac93c8686f57ea861163e2fe0552f59ba7c

Tx prefix hash: 745917deaf4197989f6e3ae156ae5d08edf7a1447c3023f729806ec916bbe256
Tx public key: b351828ecbf57ae3e06e940ad1dedb2119092e2579b3450f39e41c5e0aab7b75
Timestamp: 1696067876 Timestamp [UCT]: 2023-09-30 09:57:56 Age [y:d:h:m:s]: 01:148:00:32:38
Block: 859350 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366811 RingCT/type: yes/0
Extra: 01b351828ecbf57ae3e06e940ad1dedb2119092e2579b3450f39e41c5e0aab7b7502110000000633af99f4000000000000000000

1 output(s) for total of 0.872201361000 dcy

stealth address amount amount idx
00: 8e68c9b8abd8bee6e2cd9cb07e3d21350fcbe901444c9e8ba4d2bfdbb6fe8676 0.872201361000 1313572 of 0

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": 859360, "vin": [ { "gen": { "height": 859350 } } ], "vout": [ { "amount": 872201361, "target": { "key": "8e68c9b8abd8bee6e2cd9cb07e3d21350fcbe901444c9e8ba4d2bfdbb6fe8676" } } ], "extra": [ 1, 179, 81, 130, 142, 203, 245, 122, 227, 224, 110, 148, 10, 209, 222, 219, 33, 25, 9, 46, 37, 121, 179, 69, 15, 57, 228, 28, 94, 10, 171, 123, 117, 2, 17, 0, 0, 0, 6, 51, 175, 153, 244, 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