Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9bc505cc18c76374b708b3886f274d961a08951fa5a23bde70e083ebdaa76c94

Tx prefix hash: 96523c44c2f1af9350276fa00934556dc0504183e6ce31e83b374be9113aad2f
Tx public key: 2b109bfb8c2c37b2dbc7ce942c75962c54ad030104892f26334cc7ef25471d8d
Timestamp: 1736187461 Timestamp [UCT]: 2025-01-06 18:17:41 Age [y:d:h:m:s]: 00:124:20:19:03
Block: 1191625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 89031 RingCT/type: yes/0
Extra: 012b109bfb8c2c37b2dbc7ce942c75962c54ad030104892f26334cc7ef25471d8d02110000001e1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4101b54d12dd6a418d7fcc2e4f11099739fd6e3ffc95b02bdca2d52e0af6d2d 0.600000000000 1678166 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": 1191635, "vin": [ { "gen": { "height": 1191625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4101b54d12dd6a418d7fcc2e4f11099739fd6e3ffc95b02bdca2d52e0af6d2d" } } ], "extra": [ 1, 43, 16, 155, 251, 140, 44, 55, 178, 219, 199, 206, 148, 44, 117, 150, 44, 84, 173, 3, 1, 4, 137, 47, 38, 51, 76, 199, 239, 37, 71, 29, 141, 2, 17, 0, 0, 0, 30, 31, 10, 83, 235, 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