Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d201236c381954350a70104581b44cceb424d871a62282dee4429ae02f14e98a

Tx prefix hash: fde4c5b665bcaaa04112cdf13283df54619dccfca687d31399fdf72011b4d0ca
Tx public key: b78dc6803b73cf6b4e0154d9dbb297c02834f1eadb3cc20897e1a79f302fe7d4
Timestamp: 1724841433 Timestamp [UCT]: 2024-08-28 10:37:13 Age [y:d:h:m:s]: 01:070:18:33:42
Block: 1097690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309025 RingCT/type: yes/0
Extra: 01b78dc6803b73cf6b4e0154d9dbb297c02834f1eadb3cc20897e1a79f302fe7d4021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e80d25ca082c27224d2f3244334a8ce6f1b74567d1f207dd921b9e023cf83dbe 0.600000000000 1573143 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": 1097700, "vin": [ { "gen": { "height": 1097690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e80d25ca082c27224d2f3244334a8ce6f1b74567d1f207dd921b9e023cf83dbe" } } ], "extra": [ 1, 183, 141, 198, 128, 59, 115, 207, 107, 78, 1, 84, 217, 219, 178, 151, 192, 40, 52, 241, 234, 219, 60, 194, 8, 151, 225, 167, 159, 48, 47, 231, 212, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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