Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4bc53a1c38e73683d3e0a6e08bfc61e282fcbf24316834a4b969c7f0c4373060

Tx prefix hash: 23ce5379f0aeb8c30d20bbddb3dff711fa7538cc7ea3ac9014ea4bc3d9dc7302
Tx public key: 8b9c70c07d4c6e9c97e317a24f756d607720bc7b40ded2b7370f2dda34933296
Timestamp: 1723999333 Timestamp [UCT]: 2024-08-18 16:42:13 Age [y:d:h:m:s]: 00:222:07:33:58
Block: 1090717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158757 RingCT/type: yes/0
Extra: 018b9c70c07d4c6e9c97e317a24f756d607720bc7b40ded2b7370f2dda3493329602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a9dc91a2b82d5434c199eb8803a84751b18d59c12a4929616c996bba9c69af1 0.600000000000 1565340 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": 1090727, "vin": [ { "gen": { "height": 1090717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a9dc91a2b82d5434c199eb8803a84751b18d59c12a4929616c996bba9c69af1" } } ], "extra": [ 1, 139, 156, 112, 192, 125, 76, 110, 156, 151, 227, 23, 162, 79, 117, 109, 96, 119, 32, 188, 123, 64, 222, 210, 183, 55, 15, 45, 218, 52, 147, 50, 150, 2, 17, 0, 0, 0, 3, 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