Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab9c467b99931a37151a1b63aae12625bcac4b8acb6f3b66248a02c76b2fff1a

Tx prefix hash: 42d5ad8271a7238679331db8d40f8a3e7f2cf76a55dd982e7960f0cab12a08ba
Tx public key: b747735a80149666156503fbf1c7eb8c19aa1790732e12596f98d560f1dfa1f6
Timestamp: 1734486649 Timestamp [UCT]: 2024-12-18 01:50:49 Age [y:d:h:m:s]: 00:112:05:25:22
Block: 1177573 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79971 RingCT/type: yes/0
Extra: 01b747735a80149666156503fbf1c7eb8c19aa1790732e12596f98d560f1dfa1f6021100000001fb4d90dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f0acd926710ed62f627296a839c19b75fc5b4f0d64b61f71a675307d0085576 0.600000000000 1663944 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": 1177583, "vin": [ { "gen": { "height": 1177573 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f0acd926710ed62f627296a839c19b75fc5b4f0d64b61f71a675307d0085576" } } ], "extra": [ 1, 183, 71, 115, 90, 128, 20, 150, 102, 21, 101, 3, 251, 241, 199, 235, 140, 25, 170, 23, 144, 115, 46, 18, 89, 111, 152, 213, 96, 241, 223, 161, 246, 2, 17, 0, 0, 0, 1, 251, 77, 144, 220, 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