Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d04666892009c4dfab898a9d17296f372ed359279969242046d1e11673fc625

Tx prefix hash: f3f6e86290172a3b2b42317f84afb63136f6679c41a2a299d1e70cbd49f48176
Tx public key: 3e2ab19e0c9fcb8ae8d8e4b6c28cab5f303fa8cc741a1753278ace8730005ed3
Timestamp: 1712510008 Timestamp [UCT]: 2024-04-07 17:13:28 Age [y:d:h:m:s]: 01:040:00:39:02
Block: 995427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289617 RingCT/type: yes/0
Extra: 013e2ab19e0c9fcb8ae8d8e4b6c28cab5f303fa8cc741a1753278ace8730005ed30211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d59bd39d781986d942405f99c58f7141b9fe6b500d37629f90075a2cdd996a02 0.600000000000 1455835 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": 995437, "vin": [ { "gen": { "height": 995427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d59bd39d781986d942405f99c58f7141b9fe6b500d37629f90075a2cdd996a02" } } ], "extra": [ 1, 62, 42, 177, 158, 12, 159, 203, 138, 232, 216, 228, 182, 194, 140, 171, 95, 48, 63, 168, 204, 116, 26, 23, 83, 39, 138, 206, 135, 48, 0, 94, 211, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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