Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c9f81268f18d912e17df0112bac87c630293fde25f2ea7ac34de9d2e7594225

Tx prefix hash: 9ed96f7f42528ef599fbfcf0f05a98d9a05143ec6d7ffda9034bd53cd885baec
Tx public key: 52f43fb255c0f0ff3a4ca07e751349a135f6f2f00667d5a1de395832dfbc8212
Timestamp: 1706082383 Timestamp [UCT]: 2024-01-24 07:46:23 Age [y:d:h:m:s]: 01:287:16:31:35
Block: 942144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464413 RingCT/type: yes/0
Extra: 0152f43fb255c0f0ff3a4ca07e751349a135f6f2f00667d5a1de395832dfbc821202110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 715639d9e608ce38a0a4419bbcd00ba3f8dd6926a5cf958eba60f3191e8980e2 0.600000000000 1400310 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": 942154, "vin": [ { "gen": { "height": 942144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "715639d9e608ce38a0a4419bbcd00ba3f8dd6926a5cf958eba60f3191e8980e2" } } ], "extra": [ 1, 82, 244, 63, 178, 85, 192, 240, 255, 58, 76, 160, 126, 117, 19, 73, 161, 53, 246, 242, 240, 6, 103, 213, 161, 222, 57, 88, 50, 223, 188, 130, 18, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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