Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e5d32751afc6f12659cda520c2be31a2aec3a90c83d52fa2ed14a33cd466fca

Tx prefix hash: 1023d72bccca2855c9a9967379046757127ea540dc270aea17cbdc28d7726a51
Tx public key: c73721d71b30e15c1971df444f2ae57779b8ef1c65c9669fa7cadf255c04c2e5
Timestamp: 1681734433 Timestamp [UCT]: 2023-04-17 12:27:13 Age [y:d:h:m:s]: 01:316:21:40:14
Block: 740556 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487738 RingCT/type: yes/0
Extra: 01c73721d71b30e15c1971df444f2ae57779b8ef1c65c9669fa7cadf255c04c2e5021100000004e6d27f9c000000000000000000

1 output(s) for total of 2.158891267000 dcy

stealth address amount amount idx
00: 5cd221a49421cdffd0d4d092e07b97a677a978dfde336ff80c5135a10f90a80c 2.158891267000 1187453 of 0

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": 740566, "vin": [ { "gen": { "height": 740556 } } ], "vout": [ { "amount": 2158891267, "target": { "key": "5cd221a49421cdffd0d4d092e07b97a677a978dfde336ff80c5135a10f90a80c" } } ], "extra": [ 1, 199, 55, 33, 215, 27, 48, 225, 92, 25, 113, 223, 68, 79, 42, 229, 119, 121, 184, 239, 28, 101, 201, 102, 159, 167, 202, 223, 37, 92, 4, 194, 229, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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