Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a68ea6a9ff607ab5d095ab11e44afa60152381afc0d623ac4710721fe930987e

Tx prefix hash: 48200d0594a5eb8a942c06f571c18635047d7c25f51e014bd28a080add0cd53e
Tx public key: 70fedc13d1519de9e8b19011454d0cf1f1648c980d9d6a00f4c48d2e423b35d4
Timestamp: 1733230753 Timestamp [UCT]: 2024-12-03 12:59:13 Age [y:d:h:m:s]: 00:119:09:38:31
Block: 1167146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85118 RingCT/type: yes/0
Extra: 0170fedc13d1519de9e8b19011454d0cf1f1648c980d9d6a00f4c48d2e423b35d4021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 378a10238be0a147df1e2b6bbead724fc0f9afb5de6dea92299bd84289676159 0.600000000000 1652839 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": 1167156, "vin": [ { "gen": { "height": 1167146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "378a10238be0a147df1e2b6bbead724fc0f9afb5de6dea92299bd84289676159" } } ], "extra": [ 1, 112, 254, 220, 19, 209, 81, 157, 233, 232, 177, 144, 17, 69, 77, 12, 241, 241, 100, 140, 152, 13, 157, 106, 0, 244, 196, 141, 46, 66, 59, 53, 212, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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