Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1a1f44bd2cf3e9d1f3d397286086a9a9a920a5518bc02b7536a8994c6b72395

Tx prefix hash: 2bb994ee3593c29f4de7b21fde0a2875794fed23bf0a8bf6c2c4688f5f8d75d7
Tx public key: 6428433748b5eb1d5a97ea72127efdec690379763a550cc5d917c9e5256dca34
Timestamp: 1728240890 Timestamp [UCT]: 2024-10-06 18:54:50 Age [y:d:h:m:s]: 01:033:11:44:33
Block: 1125874 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282316 RingCT/type: yes/0
Extra: 016428433748b5eb1d5a97ea72127efdec690379763a550cc5d917c9e5256dca3402110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 20750cc7b6c430f00cca4d8c19e99f4eb1fc9c6a6a37a1b46bf0471173d85a40 0.600000000000 1608645 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": 1125884, "vin": [ { "gen": { "height": 1125874 } } ], "vout": [ { "amount": 600000000, "target": { "key": "20750cc7b6c430f00cca4d8c19e99f4eb1fc9c6a6a37a1b46bf0471173d85a40" } } ], "extra": [ 1, 100, 40, 67, 55, 72, 181, 235, 29, 90, 151, 234, 114, 18, 126, 253, 236, 105, 3, 121, 118, 58, 85, 12, 197, 217, 23, 201, 229, 37, 109, 202, 52, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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