Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b483639391ae293a4b7f2bd2b7b346aa72f53ddf9dd98c35ff1d99c6522630a4

Tx prefix hash: 3f427caa820969ca0d7a65668eca38d7cbcb2ac289b931f303ee2b4cdacee129
Tx public key: fc69ea1a293885f1fd012e775714645d522245bc96375557f198a823717a2199
Timestamp: 1704405101 Timestamp [UCT]: 2024-01-04 21:51:41 Age [y:d:h:m:s]: 01:308:07:20:35
Block: 928242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479192 RingCT/type: yes/0
Extra: 01fc69ea1a293885f1fd012e775714645d522245bc96375557f198a823717a21990211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 97cfff5e021b40cdcfaa969c869e0a7828bea0928de5e0d99faa2e55a4dc8a8a 0.600000000000 1386100 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": 928252, "vin": [ { "gen": { "height": 928242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97cfff5e021b40cdcfaa969c869e0a7828bea0928de5e0d99faa2e55a4dc8a8a" } } ], "extra": [ 1, 252, 105, 234, 26, 41, 56, 133, 241, 253, 1, 46, 119, 87, 20, 100, 93, 82, 34, 69, 188, 150, 55, 85, 87, 241, 152, 168, 35, 113, 122, 33, 153, 2, 17, 0, 0, 0, 3, 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