Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 791f49ae3d4ec50fb900b7a52b626d6a7182448d267898e881939d45f39da8e7

Tx prefix hash: f8c411a488781cd1c08b7d9bf2eeea1e0155e889aebe76627ac8d09dbefa17dd
Tx public key: c22a59356d8bd29e59eb8dedf4e51a0ea3edec024bbdd38d1a646e396d240f3f
Timestamp: 1704851156 Timestamp [UCT]: 2024-01-10 01:45:56 Age [y:d:h:m:s]: 01:099:06:48:12
Block: 931950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332073 RingCT/type: yes/0
Extra: 01c22a59356d8bd29e59eb8dedf4e51a0ea3edec024bbdd38d1a646e396d240f3f02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12b9e1d119183efa718c4139ab581cacdeb70c7104fa92b18be5276624d2d1dd 0.600000000000 1389860 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": 931960, "vin": [ { "gen": { "height": 931950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12b9e1d119183efa718c4139ab581cacdeb70c7104fa92b18be5276624d2d1dd" } } ], "extra": [ 1, 194, 42, 89, 53, 109, 139, 210, 158, 89, 235, 141, 237, 244, 229, 26, 14, 163, 237, 236, 2, 75, 189, 211, 141, 26, 100, 110, 57, 109, 36, 15, 63, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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