Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f510f1d51c7abf0691a04492f5c69faeb357bbc7fdc84e32daa1fd26ab2c4531

Tx prefix hash: 16a529d6260e89fe3e2e1ba0bbf77b03c2d91e406a5725b435e9f4d50a635001
Tx public key: 334596e896b4b28a5f215b979f0f5978c98ab88817a02dc6ef1efa2820286e56
Timestamp: 1714829377 Timestamp [UCT]: 2024-05-04 13:29:37 Age [y:d:h:m:s]: 01:249:20:03:29
Block: 1014699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437256 RingCT/type: yes/0
Extra: 01334596e896b4b28a5f215b979f0f5978c98ab88817a02dc6ef1efa2820286e5602110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fafb61b6a37917a1807a0a10667da92b6f10549d8eb202a4482731b2215a1709 0.600000000000 1477860 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": 1014709, "vin": [ { "gen": { "height": 1014699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fafb61b6a37917a1807a0a10667da92b6f10549d8eb202a4482731b2215a1709" } } ], "extra": [ 1, 51, 69, 150, 232, 150, 180, 178, 138, 95, 33, 91, 151, 159, 15, 89, 120, 201, 138, 184, 136, 23, 160, 45, 198, 239, 30, 250, 40, 32, 40, 110, 86, 2, 17, 0, 0, 0, 6, 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