Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2e959c6546960036a2f8dde1a0ae60763a15e749d7272fee4fa51d87f19ef6a

Tx prefix hash: 96743df7741f7e6904c68dcab628738208f58a53df39b801d26408c0cfcb9bd0
Tx public key: 5633e65714838c690c11ac126f2b1ab9be96c04d4f3a10661a72064054bccc1f
Timestamp: 1727302891 Timestamp [UCT]: 2024-09-25 22:21:31 Age [y:d:h:m:s]: 00:120:22:05:00
Block: 1118099 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86410 RingCT/type: yes/0
Extra: 015633e65714838c690c11ac126f2b1ab9be96c04d4f3a10661a72064054bccc1f02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 42514feb2d7739391dfd4f231a9ac6f0ebf2d467b7557796a401c2b5312df2dd 0.600000000000 1599174 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": 1118109, "vin": [ { "gen": { "height": 1118099 } } ], "vout": [ { "amount": 600000000, "target": { "key": "42514feb2d7739391dfd4f231a9ac6f0ebf2d467b7557796a401c2b5312df2dd" } } ], "extra": [ 1, 86, 51, 230, 87, 20, 131, 140, 105, 12, 17, 172, 18, 111, 43, 26, 185, 190, 150, 192, 77, 79, 58, 16, 102, 26, 114, 6, 64, 84, 188, 204, 31, 2, 17, 0, 0, 0, 1, 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